feat(@angular/build): support runtime Zone.js detection in Vitest unit test runner#32492
Merged
clydin merged 1 commit intoangular:mainfrom Mar 2, 2026
Merged
Conversation
angular-robot
bot
added
detected: feature
clydin
force-pushed
the
vitest/dynamic-zonejs-inclusion
branch
2 times, most recently
from
7e654f5 to
53cc74d
Compare
clydin
added
target: major
alan-agius4
reviewed
Feb 27, 2026
packages/angular/build/src/builders/unit-test/runners/vitest/build-options.ts
Outdated
Show resolved
Hide resolved
alan-agius4
reviewed
Feb 27, 2026
packages/angular/build/src/builders/unit-test/runners/vitest/build-options.ts
Outdated
Show resolved
Hide resolved
…t test runner This commit improves how the Vitest unit test runner handles Zone.js and its testing polyfills. Previously, the inclusion of provideZoneChangeDetection and zone.js/testing was determined solely by a build-time check for zone.js in the polyfills array. Now, the runner supports three strategies for zone.js/testing inclusion: - none: If zone.js is not installed in the project. - static: If zone.js is explicitly included in the polyfills build option. - dynamic: If zone.js is installed but not explicitly in polyfills. This uses a runtime check and dynamic import to load testing support if Zone is present. Additionally, TestBed initialization now dynamically provides ZoneChangeDetection based on the runtime presence of Zone.js, better supporting zoneless applications and implicit Zone.js loading scenarios.
clydin
force-pushed
the
vitest/dynamic-zonejs-inclusion
branch
from
53cc74d to
af37845
Compare
alan-agius4
approved these changes
Mar 2, 2026
alan-agius4
added
action: merge
Member
Author
|
This PR was merged into the repository. The changes were merged into the following branches:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit improves how the Vitest unit test runner handles Zone.js and its testing polyfills. Previously, the inclusion of provideZoneChangeDetection and zone.js/testing was determined solely by a build-time check for zone.js in the polyfills array.
Now, the runner supports three strategies for zone.js/testing inclusion:
Additionally, TestBed initialization now dynamically provides ZoneChangeDetection based on the runtime presence of Zone.js, better supporting zoneless applications and implicit Zone.js loading scenarios.